I am working now on this branch but maybe it'd be better to split the PR up. @acowley let me know what you would prefer. Also, I really don't know what the best solution is to make the Tutorial pass doctests without adding a global dependency on singletons which is a bit annoying.

How would you split it up?

There are some simple changes such as fixing or adding doctests. And there are some like the singletons version bounds that may be more complex.

I pushed a new version with open version bounds but I'm unsure how to sustainably resolve this issue because it's a pity to add a dependency on the main library just for the tutorial. Maybe best would be to keep the tutorial just in tests and then link to it from the haddock page?

That sounds reasonable regarding singletons. I agree that we should avoid making it a dependency of the library if possible.

@acowley I think I managed to run all examples, including the existing Tutorial through cabal-docspec without adding singletons as a library dependency (it is added through a dummy doctests target and then exposed through an extra field).

I think we could try activating it in CI but that's a bit difficult for me to do without access to it. In theory you should be able to run it with cabal-docspec in the base folder after building the code with cabal build all --enable-tests.

@acowley , I investigated this a bit and unfortunately it seems more complex to get a cabal-docspec binary for Mac and Windows than what I have time for right now.

Wouldn't it be sufficient to just run the doctests on the Linux CI? As opposed to the build, I don't think testing the docs cross platform adds much extra value. And for development on mac, maybe the cabal-docspec Docker container works until there is a proper binary available?

Yes, running only in CI is definitely an option. I was going to take a look at a from source build of cabal-docspec, did anything in particular not work out when you looked at it or was it just a big pain?

Nothing in particular except for various general comments in the cabal-extras repo on the build process that may indicate complexity. But it's probably more because I'm not super experienced with the Nix Haskell infra, I fear I can't really debug any Macos or Windows builds, and I don't have enough headspace at the moment to dive into that 🙄. I want to mostly add documentation to vinyl and frames and maybe make some smaller improvements since I tried using those more actively recently.

I also wonder what the proper way forward is so that we don't duplicate effort that should find it's place upstream. But considering all options (eg hackage doesn't seem to be in sight), I think writing a cross platform flake for cabal-extras seems like the most reasonable thing to do.

Wow, cabal-extras is pretty deeply idiosyncratic. I'm not sure if it's worth trying to make its individual parts look more like normal packages. Definitely open to the CI-only solution.

@acowley , sorry this ready except for running it cleanly in the CI. I think it's a useful addition but I'm a bit blocked on my own. Do you think we can somehow finish it together?

ping @acowley